OpenEdge Getting Started:<br />WebSpeed Essentials Testing the Web server

Before you can test the Web server, you must have at least one WebSpeed broker. In addition, make sure that the Web server is running, and that the NameServer and AdminService is properly configured.

Verify that the Web server is running.

Start a Web browser. (Internet Explorer Version 6.0 or later is recommended.)

Use ping functionality to determine if connectivity exists between the Web server and WebSpeed components. To accomplish this, conduct a round-trip test from the browser to a WebSpeed agent using the CGI Messenger (cgiip.exe). This test instructs the Messenger to make a connection to the broker and an available agent.

An example of ping for a Web server in Windows follows:


http://localhost/scipts/cgiip.exe/ping.

An example of ping for a Web server on Linux or UNIX follows:


http://localhost/scipts/cgi-bin/wspd_cgi.sh/ping.

Note: The host name (identified as localhost in the example) differs depending upon the environment in which WebSpeed operates; your installation choice (for example, on a local machine) dictates the path.

Verifying connectivity without a Web server

In general, testing Web server connectivity is accomplished using an existing connection to a server. However, in some cases, connectivity to a server might not be feasible. In such cases, you can invoke a procedure to verify connectivity without using a browser or Web server by establishing a pseudo Web request to cgiip and the WebSpeed Transaction Broker.

Execute the following command from a command prompt (or a batch file) to test connectivity without the presence of a Web server:

Where broker is the name of the WebSpeed broker, host_broker is the name of the machine where the broker resides, and port_number is the port for the Web Server.

After executing the script, a successful connection to the Web server generates a message similar to “The WebSpeed Dispatcher is running.” If WebSpeed is unable to establish a connection to the server, an error message similar to the following is generated: “WebSpeed error from messenger process. Failure connecting to WebSpeed Transaction Broker! Verify the Broker has been started. Verify the specified port number is the same as the “Port” option in the WebSpeed Transaction Broker configuration file. Error: -63.”